Revised text and headers to adhere to style guide #520
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Edit the text and titles to adhere to style guide rules.
|
✅ All required contributors have signed the F5 CLA for this PR. Thank you! |
github-actions
bot
added
documentation
|
I have hereby read the F5 CLA and agree to its terms |
|
Where should I comment for license?
Best,
Megan
…On Sun, May 4, 2025 at 4:01 PM github-actions[bot] ***@***.***> wrote:
*github-actions[bot]* left a comment (nginx/documentation#520)
<#520 (comment)>
🎉 Thank you for your contribution! It appears you have not yet signed the F5
Contributor License Agreement (CLA)
<https://github.com/f5/.github/blob/main/CLA/cla-markdown.md>, which is
required for your changes to be incorporated into an F5 Open Source
Software (OSS) project. Please kindly read the F5 CLA
<https://github.com/f5/.github/blob/main/CLA/cla-markdown.md> and reply
on a new comment with the following text to agree:
------------------------------
I have hereby read the F5 CLA and agree to its terms
------------------------------
You can retrigger this bot by commenting *recheck* in this Pull Request. Posted
by the *CLA Assistant Lite bot*.
—
Reply to this email directly, view it on GitHub
<#520 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJVTBNSYZTB46JN5NU4BKTD242L4XAVCNFSM6AAAAAB4NMLXAWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNBZGQ4DKMZXHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
mjang
requested changes
May 5, 2025
content/nginx/deployment-guides/amazon-web-services/high-availability-keepalived.md
Outdated
Show resolved
Hide resolved
content/nginx/deployment-guides/amazon-web-services/high-availability-keepalived.md
Outdated
Show resolved
Hide resolved
content/nginx/deployment-guides/amazon-web-services/high-availability-keepalived.md
Outdated
Show resolved
Hide resolved
content/nginx/deployment-guides/amazon-web-services/high-availability-keepalived.md
Outdated
Show resolved
Hide resolved
content/nginx/deployment-guides/amazon-web-services/high-availability-keepalived.md
Outdated
Show resolved
Hide resolved
content/nginx/deployment-guides/amazon-web-services/high-availability-keepalived.md
Outdated
Show resolved
Hide resolved
content/nginx/deployment-guides/amazon-web-services/high-availability-keepalived.md
Outdated
Show resolved
Hide resolved
content/nginx/deployment-guides/amazon-web-services/high-availability-keepalived.md
Outdated
Show resolved
Hide resolved
content/nginx/deployment-guides/amazon-web-services/high-availability-keepalived.md
Outdated
Show resolved
Hide resolved
content/nginx/deployment-guides/amazon-web-services/high-availability-keepalived.md
Outdated
Show resolved
Hide resolved
|
recheck |
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
Co-authored-by: Mike Jang <[email protected]>
|
Hi Mike, I looked at your feedback. I 'Committed' you edits. Please let me know if that was the wrong process. Thank you again for your patience. |
|
Thanks so much and congratulations on your contribution! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Problem: Revised the text and the headers of the document to adhere to style guide.
Please focus on (optional): I tried to make the body text easier to read and used sentence case on a few of the sub headings.
If this PR addresses an issue on GitHub, ensure that you link to it here: (#95)
Closes #ISSUE
Checklist
Before merging a pull request, run through this checklist and mark each as complete.
README.mdandCHANGELOG.mdFootnotes
Potentially sensitive changes include anything involving code, personally identify information (PII), live URLs or significant amounts of new or revised documentation. Please refer to our style guide for guidance about placeholder content. ↩